A business object is an iMIS system construct representing the data elements and business rules of a business concept like a contact; it is implemented using a combination of business rules, a schema definition that describes the data structures of the object’s properties, and a database view.
The iMIS Business object model sets the framework and foundation for most significant iMIS application objects such as customers, orders, products, inventory, tasks, etc. All iMIS Business objects share a common construction methodology and standard ways of expressing their properties, attributes, and methods. iMIS business objects are extensible and customizable via the Business Object Designer.
Using the .NET Dataset Object Model
The iMIS business object base classes are based upon the .NET DataSet object model. The .NET DataSet is the main target for data handling as created by the .NET design engineers. Modeling over the .NET DataSet and constituent components has a number of advantages and implications:
■ iMIS business objects basically appear just like .NET datasets.
■ iMIS business objects support automatic binding in the development and runtime environment.
■ All objects automatically have an XML representation.
■ iMIS business objects utilize the standard DataSet constructs to share and express data and metadata.
■ The term “metadata” is frequently defined literally as “data about data”. In the context of iMIS business objects, metadata is the structured, persistent data about business object resources, their characteristics, and their behavior.
■ All of the properties are exposed to the outside world in the Dataset table/column/row object model.
Base classes for business objects
Business objects are implemented by inheritance from core .NET classes, specific to ADO.NET. This means that the features and power of the base class are available to the business object base classes.
■ BusinessContainer – Container of business objects and their instances. Corresponds to a .NET Dataset (System.Data.DataSet class).
■ BusinessController – Collection of business object instances and implementer of business logic. Corresponds to a DataTable (System.Data.DataTable class).
■ BusinessItem – Contains a single instance of a business object. Corresponds to a DataRow (System.Data.DataRow class).
Benefits of iMIS business objects
This table summarizes the significant gains that business objects bring to the management and protection of both data and business rules:
|
Feature/Benefit |
Example |
|
.NET centric |
Auto-binding to runtime controls. Can be passed through web services. Database persistence and persistence engine ready made. XML ready. .NET standard metadata structures. |
|
Automatically implements standardized object and column security for all objects |
Keep sensitive data from entire staff or user population. |
|
New types of objects |
User-defined tables, survey, application forms, etc. |
|
New columns |
Extend product, order, referral, opportunities, issue management definitions. |
|
Standard interface for all objects |
Can be used directly by query tools, workflow, screen painters, export utilities, mail merge utilities, etc. |